System for measuring video playback events using a server generated manifest/playlist

ABSTRACT

An apparatus and method for managing video playback is disclosed. In one aspect, a server may be used to generate a manifest file for directing a video player to play requested video content in a video stream with alternative content.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of U.S. patent application Ser. No. 15/590,973, filed May 9, 2017, which claims priority to U.S. Provisional Patent Application No. 62/334,143, entitled “Method and Apparatus for Tracking Video Playback Events Using a Server Generated Manifest/Playlist,” and U.S. Provisional Patent Application No. 62/334,221, entitled “Method and Apparatus for In-Band Metadata Tunneling for Frame Accurate Downstream Video Player Control,” each filed on May 10, 2016, all of which are herein incorporated by reference.

BACKGROUND

The subject matter disclosed herein relates to a method for measuring video playback events during video streaming which may be unique to each user. More specifically, a method and apparatus for using a server to generate per-user manifest files for providing unique viewing experiences and proxy modules local to video players receiving the manifest files for measuring video playback events with frame accuracy is disclosed.

Video streaming allows video content to be delivered to a video player via the Internet. The video content is a video signal generated by a content provider for distribution to video consumers. The video signal may be provided in an uncompressed file format, such as a serial digital interface (SDI) format, or in a compressed format, such as a Moving Picture Experts Group (MPEG) file format or Transport Stream (TS) file format. The video signal is sent to an encoder which converts the file into a live streaming signal. The live streaming signal is preferably a segmented data stream that may be transmitted using standard Hypertext Transport Protocol (HTTP) over the internet. The live streaming signal may include multiple streams, where each stream may have a different data rate and/or different resolution.

Two common formats for the live streaming signal include HTTP Live Streaming (HLS) implemented by Apple® and MPEG-Dynamic Adaptive bitrate Streaming over HTTP (MPEG-DASH) implemented, for example, by web browsers such as Chrome®, Microsoft Edge®, and Firefox®. In addition to the segmented data stream, the encoder generates a manifest file. The manifest file contains information for a video player to play the segmented data stream such as the data rate and resolution of each stream and a playlist providing an address from which the video content may be retrieved. Historically, the encoder has generated a single manifest file for each encoded video signal, where the manifest file is distributed along with the streaming signal.

The live streaming signal and the manifest file are stored in one or more Content Delivery Networks (CDN). Each CDN includes a number of edge servers which store the streaming signal and manifest file until requested by a video player. When the streaming signal is provided via to multiple CDNs, the CDNs may be in different geographic locations, such as the West Coast, East Coast or Midwest. Each video player may select a CDN based, among other things, on its geographic proximity in order to reduce transmission latencies.

The video player may be any suitable electronic device to receive the streaming signal such as a desktop computer, a television, a laptop computer, a tablet, or a mobile phone. A user initiates a request to view desired video content on the video player. The video player includes video management software executing on the video player which has knowledge of the address of the CDN and which may provide a list of video content stored on the CDN to the user. After the user has selected a desired video, the video player, in turn, requests that the video content be transmitted from the CDN.

As is further known to those skilled in the art, it is often desirable to integrate advertising or other alternative content with requested video content in order, for example, to produce revenue which may ultimately support the requested video content. To ensure the effectiveness of such alternative content, it is often desirable by producers of the alternative content to require the video player to measure various aspects of the alternative content being displayed. This may be accomplished, for example, via metadata provided with the alternative content for instructing the video player. Such aspects for measuring may include, for example, the precise time in which the alternative content starts, stops, and/or reaches a midpoint with respect to the requested video content, a Uniform Resource Locator (URL) address for the video player, and so forth. One example of a standard for communication between a server and video player for measuring such aspects of alternative content is the Video Ad Serving Template (VAST) specification released by the Interactive Advertising Bureau (IAB).

In addition, as is further known to those skilled in the art, it is often desirable to provide unique viewing experiences to users viewing the same requested video content. For example, although different users may request to view identical video content, such as an episode of a television show or a movie, the users may be in entirely different geographic locations and/or may have entirely different viewing histories. Such differences may make the display of certain alternative content much more desirable than other alternative content. The desire to providing unique viewing experiences for users while also ensuring the effectiveness of alternative content by measuring the various aspects of the alternative content being displayed creates a significant technological challenge.

In addition, the owner or distributor of the video content may desire to provide other information to the user, such as a title of a show, programming change information, breaking news, or the like. However, such information may be geographic specific and it may be undesirable to provide the content within the video stream to all users. Still other information may not be available directly to the content provider. Rather than including such information in the video stream, a trigger is embedded within the video content alerting the video player of the presence of such content. Upon receiving the trigger, the video player makes a pull-request to a content server outside, or out-of-band, of the video stream. The content server returns the appropriate content for the video player to display along with the video stream.

However, out-of-band requests made by individual video players result in the metadata being displayed at different times with respect to the video content being delivered. Different video players are connected to the CDN via networks having different bandwidths, different switching devices and the like that result in varying transmission delays. Similarly, the video players are connected to the content server via networks having different bandwidths, different switching devices and the like that result in varying transmission delays. Thus, the delivery of the video content from the CDN and the delivery of content indicated from the metadata happen asynchronously, and the content indicated by the metadata, therefore, cannot be displayed synchronized with a particular frame of the video transmission. Therefore, it would be desirable to provide a system with frame accurate playback of metadata.

Historically, metadata has been used in large part to identify programming, segments of video, commercial breaks and the like. These inserted data were based on the television model in which a passive user watches video presented by the content provider. However, streaming video services provide a more interactive experience. The video content may be provided on a computer, mobile phone, or other device which provides user input. Thus, it would be desirable to provide a system which allows insertion of interactive metadata, requiring or soliciting a response from a user of the video device.

BRIEF DESCRIPTION OF THE DISCLOSURE

The subject matter disclosed herein describes an apparatus and method for using a server to generate per-user manifest files for providing unique viewing experiences and proxy modules local to video players receiving the manifest files for measuring video playback events with frame accuracy. In one aspect, a server may be used to generate a manifest file for directing a video player to play requested video content in a video stream with advertising or other alternative content which may be desired. A proxy module local to the video player may parse the video stream to inject triggers at frame accurate locations which may be desired for measuring, such as at a precise frame in which the alternative content starts, stops, and/or reaches a midpoint with respect to the requested video content. The proxy module may redirect the video player to the parsed and injected (modified) video stream so that the video player produces a detectable event at each trigger which may be measured by a server.

An apparatus or method capable of frame accurate playback of metadata and that allows insertion of interactive metadata in a video stream is also disclosed. A video manager is in communication with an encoder to inject metadata in a video stream. In one embodiment, the video manager may receive a trigger inserted in the video stream by the content provider and retrieve metadata from a content server corresponding to the trigger. In another embodiment, the video manager may further include a user interface operative to receive metadata from a third party. The video manager may then insert the metadata into the video stream at a desired frame location for delivery to a video player.

In one embodiment, a system for managing video playback may comprise: a manifest server configured to communicate with a video player and a content delivery network, the manifest server executing a program stored in a non-transient medium operable to: (a) receive a request from a video player for playing a video stream comprising requested content; (b) upon receiving the request: (i) communicate with a first content delivery network to obtain a first manifest file containing information for allowing a video player to play the requested content; and (ii) communicate with a second content delivery network to obtain information for allowing a video player to play alternative content and produce a detectable event in connection with the alternative content; and (c) modify the first manifest file to produce a second manifest file unique to the video player having the request, the second manifest file containing information for allowing the video player to play the requested content and the alternative content and produce the detectable event.

According to another embodiment, a method for managing video playback using a manifest server configured to communicate with a video player and a content delivery network may comprise: (a) receiving a request from a video player for playing a video stream comprising requested content; (b) upon receiving the request: (i) communicating with a first content delivery network to obtain a first manifest file containing information for allowing a video player to play the requested content; and (ii) communicating with a second content delivery network to obtain information for allowing a video player to play alternative content and produce a detectable event in connection with the alternative content; and (c) modifying the first manifest file to produce a second manifest file unique to the video player having the request, the second manifest file containing information for allowing the video player to play the requested content and the alternative content and produce the detectable event.

According to another embodiment, a system for managing video playback may comprise: an encoder configured to convert video content from a content provider to a segmented video stream for delivery to a video player; and a video manager in communication with the encoder, the video manager executing a program stored in a non-transient medium operable to: (a) receive metadata for insertion into a video stream; and (b) insert the metadata at a desired frame location within the video stream.

These and other objects, advantages, and features of the disclosure will become apparent to those skilled in the art from the detailed description and the accompanying drawings. It should be understood, however, that the detailed description and accompanying drawings, while indicating various embodiments of the present disclosure, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the present disclosure without departing from the spirit thereof, and the disclosure includes all such modifications.

BRIEF DESCRIPTION OF THE DRAWING(S)

Various embodiments of the subject matter disclosed herein are illustrated in the accompanying drawings in which like reference numerals represent like parts throughout, and in which:

FIG. 1 is a block diagram representation of an environment incorporating the method for measuring video playback using manifest files generated by a server of the present disclosure;

FIG. 2 is a flow diagram illustrating the measuring of video playback using manifest files generated by a server according to one embodiment of the disclosure;

FIG. 3A is a video signal divided into video segments, and FIG. 3B is a modified video signal stitched to include alternative content segments, each according to an embodiment of the disclosure;

FIG. 4 is a segment of a manifest file describing the bandwidths of the available streams for the streaming video content and the location of each stream according to one embodiment of the disclosure;

FIG. 5 is a segment of a manifest file including a portion of a playlist according to one embodiment of the disclosure;

FIG. 6 is a block diagram representation of an environment for delivering streaming video with per-user manifest generation;

FIG. 7 is a flow diagram illustrating per-user video manifest generation and playback; and

FIG. 8 is a screen shot of a user interface executing on a video manager for selection of metadata to insert into a video stream according to one embodiment of the disclosure.

In describing the various embodiments of the disclosure which are illustrated in the drawings, specific terminology will be resorted to for the sake of clarity. However, it is not intended that the disclosure be limited to the specific terms so selected and it is understood that each specific term includes all technical equivalents which operate in a similar manner to accomplish a similar purpose. For example, the word “connected,” “attached,” or terms similar thereto are often used. They are not limited to direct connection but include connection through other elements where such connection is recognized as being equivalent by those skilled in the art.

DETAILED DESCRIPTION OF THE DISCLOSURE

The various features and advantageous details of the subject matter disclosed herein are explained more fully with reference to the non-limiting embodiments described in detail in the following description.

Turning initially to FIG. 1, one environment for measuring video playback using manifest files generated by a server is illustrated. A content provider 110 generates a video signal 112 to be distributed to video consumers. The video signal may be provided in an uncompressed file format, such as a SDI format, or in a compressed format, such as an MPEG or TS file format. The video signal 112 is sent to an encoder 114 which converts the file into a live streaming signal 116. The live streaming signal 116 is preferably a segmented data stream that may be transmitted using standard HTTP or HTTPS protocol over the internet. The live streaming signal 116 may include multiple streams, where each stream may have a different data rate and/or different resolution. The format of the live streaming signal may be, but is not limited to, HLS or MPEG-DASH. Still other protocols such as HTTP Dynamic Streaming (HDS) from Adobe® or Microsoft® Smooth Streaming and the like may be used without deviating from the scope of the disclosure.

In addition to the segmented data stream, the encoder generates a manifest file. The manifest file contains information for a video player 122 to play the segmented data stream such as the data rate and resolution of each stream and a playlist providing an address from which the video content may be retrieved. The encoder 114 generates a single manifest file for each encoded video signal, where the manifest file is distributed along with the streaming signal 116 and stored on a CDN 118. Each CDN 118 includes a number of edge servers 120 which store the encoded video signal 116 and manifest file until playback of the video content is requested by a video player 122. Although the embodiment illustrated in FIG. 1 shows a single CDN 118, it is contemplated that the encoded video signal 116 may be stored on multiple CDNs 118. The manifest file may include an address of each CDN such that playback may occur from any of the CDNs 118.

As further illustrated in FIG. 1, the environment includes a manifest server 124. The manifest server 124 is used to provide a unique manifest file, also referred to herein as a per-user manifest file, to each video player 122 for each requested video content. Each video player 122 includes a native video player module 128 which provides an interface to a user and which manages video playback on the video player 122. Each video player 122 also includes a proxy module 129. The proxy module 129 may be a plug-in or other software module executing on the video player 122 that either complements (i.e., adds additional capabilities) or replaces (i.e., adds additional capabilities and incorporates the video interface and playback capabilities) the native video player module 128. As will be discussed in more detail below, in one aspect, when a user 125 requests video content for playback on the video player 122, the native video player module 128 may communicate with the proxy module 129 and, in turn, with the manifest server 124 (rather than the CDN 118) to obtain the manifest files for video playback. The manifest server 124 manages the retrieval and delivery of the manifest file generated by the encoder 114 to provide the unique manifest file to each video player 122.

As further illustrated in FIG. 1, the environment may also include one or more Alternative Content Networks (ACN) 123 and/or an alternative content measurer 127. Alternative content, such as commercial advertisements and the like, may be stored in the ACN 123. Although the embodiment illustrated in FIG. 1 shows a single ACN 123, it is contemplated that alternative content may be stored on multiple ACNs 123 in different geographic locations. Each ACN 123 may include a number of edge servers 121 which may store a streaming signal for the alternative content until requested by the manifest server 124. The manifest server 124 may select an ACN 123 based, among other things, on its geographic proximity in order to reduce transmission latencies. The alternative content measurer 127 may be in communication with the video player 122 for measuring detectable events reported by the video player 122 in the video stream, such as triggers that are injected in relation to the alternative content, for a measuring server.

Turning next to FIG. 2, the operations performed to measure video playback using manifest files generated by a server are illustrated. At block 130, the encoder 114 receives the initial video signal 112. It is contemplated that this video signal 112 may be a pre-recorded signal, such as an episode of a television show or a movie, or the video signal 112 may be a live stream, for example, of a sporting event, concert, or news feed. The encoder 114 converts the original video signal into a live streaming signal 116 suitable for delivery via HTTP or HTTPS. One operation in converting the video signal is to divide the video signal into segments. The segments may be, for example, 10 seconds in length. Optionally, other segment lengths, for example, from 1 second up to 10 seconds may be selected. The length of the video segment must be less than the maximum payload for an HTTP data packet. Referring briefly to FIG. 3A, a video signal 116 from the encoder 114, shown by way of example, may consist of video content being divided into nine segments of requested video content, illustrated as “c1,” “c2,” “c3,” and so forth, with each segment being 10 seconds in length for a net content length of 90 seconds. After generating the video signal 116 into segments (also referred to as requested video content), the video signal and a manifest file are transmitted to the CDN 118 for storage in one of the edge servers 120, as shown in block 132.

At block 134, a user 125 then requests playback of a desired video segment on the video player 122 via the native video player module 128. The video player 122 may be any suitable electronic device to receive the streaming signal 116 such as a desktop computer, a television, a laptop computer, a tablet, Wi-Fi enabled device connected to a video screen, or a mobile phone. At block 136, the native video player module 128, in turn, requests a manifest file from the proxy module 129 in order to retrieve the information necessary to play the requested video content.

At block 138, the proxy module 129, in turn, requests the manifest file from the manifest server 124. When the video player 122 requests the manifest file from the manifest server 124 a connection is established between the devices. A session identifier may also be generated to identify the connection. The session identifier may be generated by the video player 122 or the manifest server 124. For purposes of illustration, it may be assumed that the session identifier may be generated by the video player 122. The session identifier may be transmitted to the manifest server 124 by the video player 122 when requesting a manifest file.

Because the manifest server 124 has established a connection with video player 122, it may customize the manifest file prior to returning the manifest file to the video player 122 and provide a unique manifest file to each video player 122. Without the manifest server 124, the video player 122 retrieves the manifest file directly from the CDN 118 and the content of the manifest file is the same for all users. However, because the manifest server 124 is providing a unique manifest file to each player, the manifest file may include identifying information of the video player 122, the user 125 of the video player, or a combination thereof. Further, the manifest file may be modified to include content specific for the user 125.

At block 140, the manifest server 124 communicates with the ACN 123 to request alternative content which may apply to the user 125 and/or the video player 122. Such alternative content may depend, for example, on the geographic location and/or viewing history of the user 125 and/or the video player 122, among other things. The alternative content may be used, for example, to provide advertisements or other alternative content at the beginning or end or during break segments of the requested video content. The manifest server 124 may request alternative content from the ACN 123 for every user session and for every display opportunity. At block 142, the ACN 123 returns the alternative content that may ultimately be stitched in the video stream for the video player 122.

To ensure the effectiveness of the alternative content, the alternative content may include a payload (alternative content payload information) containing specific event triggers and/or request for corresponding user-session specific data for measuring the alternative content at the video player 122. This may be accomplished, for example, via metadata provided with the alternative content for instructing the video player 122 to respond. Such event triggers may include, for example, triggering the video player 122 to respond at a precise time in which a frame of the alternative content starts, stops, and/or reaches a midpoint with respect to the requested video content, to respond with a URL address for the video player 122, and so forth.

Next, at block 144, the manifest server 124 communicates with the CDN 118, and at block 146, the latest manifest file corresponding to the particular user's request is loaded from the CDN 118. The manifest server 124 may periodically load updates for the manifest file from the CDN 118 as may be required. At block 146, the CDN 118 provides the manifest file and/or updates to the manifest server 124. In turn, the manifest server 124 processes the manifest file from the CDN 118 to determine suitable positions for stitching alternative content. In one aspect, such positions may be predetermined in the manifest file by the encoder 114.

Accordingly, the manifest server 124 updates the manifest file to include alternative content segments in the video stream as appropriate. For example, referring briefly to FIG. 3B, with a customized manifest file generated, the video signal 116 may be reconfigured for playback as a modified video signal 116′ including two segments of alternative content, illustrated as “a1” and “a2, followed by four segments of requested video content, illustrated as “c1,” “c2, “c3” and “c4, followed by another two segments of alternative content, illustrated as “a2” and “a3, and followed by another four segments of requested video content, illustrated as “c5,” “c6, “c7” and “c8.” With segments being 10 seconds in length, the modified video signal 116′ may then have a gross content length of 130 seconds. This stitched video stream may reflect, for example, enforcement of a logic rule by the manifest server 124 requiring initial viewing of a first advertisement and a midstream viewing of a second advertisement for a first time viewing of the requested video content at the video player 122. Each time the user 125 plays a video, the video player 122 may obtain an updated manifest file from the manifest server 124. The manifest server 124 may individually measure a status of the video player 122 and the user view experiences.

With reference also to FIGS. 4 and 5, segments of manifest files are illustrated that illustrate a portion of the content that may be available in a manifest file. The manifest file is a text file and the particular content on each line of the text file is identified by the directive at the start of the line. For example, FIG. 4 identifies four different streams in the streaming signal 116 where each stream has a different bandwidth. The location of a playlist for each of the streams is also included in the manifest file. FIG. 5 is another manifest file which contains a portion of the playlist of a video segment. Each line may identify a particular video segment between 1 and 5 (i.e., the “−1”, “−2”, etc . . . prior to the .ts file extension), and provides the location of video segment in the CDN 118. The manifest file may include any information corresponding to the video stream, such as metadata information for the video stream.

In addition, while segments of manifest file are updated to provide alternative content, the aforementioned alternative content payload for measuring may also be added to the manifest file. Referring again to FIG. 2, at block 148, the manifest server 124 transmits the updated manifest file to the proxy module 129.

Next, at block 150, the proxy module 129 parses the updated manifest file and extracts the alternative content payload information for measuring and stores this information in memory. The proxy module 129 then determines a frame position for the start of each alternative content segment. The proxy module 129 may utilize the updated manifest file to modify the video stream accordingly, such as by replacing the video segments (TS file location) in the manifest file with a proxy location for the video segments (TS proxy file location) provided by the proxy module 129. As a result, when the video player 122 makes a request for the video stream, the video segments at the proxy location may be provided. In addition, while replacing the video segments, the alternative content payload information for measuring, including metadata, position information, and the like, or references to such information, may be included as well. This newly updated manifest file, manipulated by proxy module 129 with the video segments at the proxy location, is then sent to the native video player module 128.

At block 152, upon receiving a manifest file pursuant to its request, the native video player module 128 may then request the video segments to display. As the manifest file now includes a proxy location for the video segments, the native video player module 128 will request the video segments from the proxy module 129.

At block 154, the proxy module 129 communicates with the CDN 118 to request video content segments; and at block 156, the proxy module 129 loads the video content segments from the CDN 118. Before the video content segments are sent to the native video player module 128, the proxy module 129 may re-package the video content segments with the alternative content segments and may inject frame accurate triggers, such as according to the ID3 standard for metadata, to form the video stream. These triggers may be set for measuring the alternative content segments, or references to the alternative content segments, with the alternative content payload information by triggering on events such as the video player 122 displaying a start, stop, and/or midpoint frame of alternative segments. Accordingly, the proxy module 129 may load the video stream (TS file) with the video content segments, alternative content segments and frame accurate triggers corresponding to the alternative content payload information.

At block 158, the proxy module 129 provides the video stream to the native video player module 128 which, in turn, plays the video stream to the user 125. Upon playback, the video player 122 will trigger upon the predetermined frame triggers which have been injected according to the alternative content payload information. These triggers may result in detectable events which may be measured by a server for measuring information about the video player 122 playing the video stream.

At block 160, the video player 122, via the native video player module 128, may play the video stream for the user 125. The user 125, in turn, may further interact with the video player 122, such as to seek forward or backward in the video stream, request a new video content, and the like. In addition, at block 162, the video player 122, via the proxy module 129, may trigger upon detectable events, such as the frame accurate triggers corresponding to the alternative content payload information, as the video stream is being played. Such detectable events may be measured by one or more servers or other utilities, such as the alternative content measurer 127.

Turning next to FIG. 6, according to another aspect of the disclosure, a content provider 210 generates a video signal 212 to be distributed to video consumers. The video signal may be provided in an uncompressed file format, such as a SDI format, or in a compressed format, such as an MPEG or TS file format. The video signal 212 is sent to an encoder 214 which converts the file into a live streaming signal 216. The live streaming signal 216 is preferably a segmented data stream that may be transmitted using standard HTTP or HTTPS protocol over the internet. The live streaming signal 216 may include multiple streams, where each stream may have a different data rate and/or different resolution. The format of the live streaming signal may be, but is not limited to, HLS or MPEG-DASH. Still other protocols such as HTTP Dynamic Streaming (HDS) from Adobe® or Microsoft® Smooth Streaming and the like may be used without deviating from the scope of the disclosure.

In addition to the segmented data stream, the encoder generates a manifest file. The manifest file contains information for a video player 222 to play the segmented data stream such as the data rate and resolution of each stream and a playlist providing an address from which the video content may be retrieved. The encoder 214 generates a single manifest file for each encoded video signal, where the manifest file is distributed along with the streaming signal 216 and stored on a CDN 218. It is noted that the “single” manifest file refers to a common or identical manifest file for each encoded signal. The manifest file may be comprised of multiple data files stored on the CDN where each manifest file contains a portion of the data required to playback the streaming signal. Further, for live streaming video, the manifest file may be updated and retransmitted at a periodic interval as new content is added from the live event. Although multiple files are used, the content generated by the encoder 214 for delivery to each video player 222 is the same. Each CDN 218 includes a number of edge servers 220 which store the encoded video signal 216 and manifest file until playback of the video content is requested by a video player 222. Although the embodiment illustrated in FIG. 6 shows a single CDN 218, it is contemplated that the encoded video signal 216 may be stored on multiple CDNs 218. The manifest file may include an address of each CDN such that playback may occur from any of the CDNs 218.

As further illustrated in FIG. 6, the exemplary environment includes a manifest server 224. The manifest server 224 is used to provide a unique manifest file, also referred to herein as a per-user manifest file, to each video player 222 for each requested video content. Each video player 222 includes a native video player module 228 which provides an interface to a user and which manages video playback on the device 222. Some video players 222 may further include an enhanced video player module 229, illustrated as an optional module in FIG. 6. The enhanced video player module 229 may be a plug-in or other software module executing on the video player 222 that either complements (i.e., adds additional capabilities) or replaces (i.e., adds additional capabilities and incorporates the video interface and playback capabilities) the native video player module 228. As will be discussed in more detail below, when a user 225 requests video content for playback on the video device 222, the native or enhanced video player module 229 communicates with a manifest server 224 rather than the CDN 218 to obtain the manifest files for video playback. The manifest server 224 manages the retrieval and delivery of the manifest file generated by the encoder 214 to provide the unique manifest file to each video player 222.

The exemplary embodiment further includes a video manager 215 in communication with the encoder 214. The video manager 215 receives triggers included from the content provider in the video signal 212. The video manager 215 is also in communication with a content server 217 and the manifest server 224, where the content server 217 may store metadata generated by the content provider 210 and which was previously retrieved via out-of-band methods by the video player 222. According to one embodiment of the disclosure, the video manager 215 and the manifest server 224 are implemented on a single server. According to another embodiment of the disclosure, the video manager 215 and the manifest server 224 are implemented on separate servers. Because the manifest server 224 has established a per-user connection with each video player 222, as discussed in more detail below, the video manager 215 can identify content intended for individual video players 222 based on the per-user connection. Upon detecting a trigger in the video signal 212, the video manager 215 contacts the content server 217 to retrieve the metadata corresponding to the trigger that would otherwise need to be requested out-of-band by the video player 222. The metadata may be universal to all video players 222 or may be tailored, for example, to a geographic region or to a particular video player 222. Having retrieved the information, the video manager communicates the information to the encoder 214 where it may be included within the transport stream for delivery directly to the video player. Insertion of the information into the video stream is discussed in more detail below.

Turning next to FIG. 7, the operations performed to create, deliver, and playback a per-user manifest file are illustrated. At block 230, the encoder 214 receives the initial video signal 212. It is contemplated that this video signal 212 may be a pre-recorded signal, such as an episode of a television show or a movie, or the video signal 212 may be a live stream, for example, of a sporting event, concert, or news feed. The encoder 214 converts the original video signal into a live streaming signal 216 suitable for delivery via HTTP or HTTPS. One operation in converting the video signal is to divide the video signal into segments. The segments may be, for example, 10 seconds in length. Optionally, other segment lengths, for example, from 1 second up to 10 seconds may be selected. The length of the video segment must be less than the maximum payload for an HTTP data packet.

After converting the video signal 212 into segments, the encoder 214 can encrypt the video signals 212 to prevent unauthorized viewing of the video content. At block 232, the encoder 214 establishes communication with a key server 226 and requests a key to use for encrypting the segmented video signal 212. The key server 226 returns a key to the encoder 214 as shown in block 234. The key used to encrypt the segmented video signal 212 will be referred to herein as the content encryption key. The encoder 214 may use any suitable encryption protocol, such as the Advanced Encryption Standard (AES), to encrypt the segmented video signal using the content encryption key. The location of the key server and the encryption key used to encrypt the segmented video signal is included in a manifest file. The manifest file and the encrypted video signal are then transmitted to the CDN 218 for storage in one of the edge servers 220, as shown in block 236.

At block 238, a user 225 then requests playback of a desired video segment on the video player 222. The video player 222 may be any suitable electronic device to receive the streaming signal 216 such as a desktop computer, a television, a laptop computer, a tablet, Wi-Fi enabled device connected to a video screen, or a mobile phone. The video player 222 requests a manifest file from the manifest server 224 in order to retrieve the information necessary to play the requested video content. With reference again to FIGS. 4 and 5, segments of exemplary manifest files are illustrated that illustrate a portion of the content that may be available in a manifest file. The manifest file is a text file and the particular content on each line of the text file is identified by the directive at the start of the line. For example, FIG. 4 identifies four different streams in the streaming signal 216 where each stream has a different bandwidth. The location of a playlist for each of the streams is also included in the manifest file. FIG. 5 is another manifest file which contains a portion of the playlist of an encrypted video segment. Each line begins with the location of the key server to decrypt the video segment, identifies a particular video segment between 1 and 5 (i.e., the “−1”, “2”, etc . . . prior to the .ts file extension), and provides the location of video segment in the CDN 218. The manifest file may include any information corresponding to the video stream, such as metadata information for the video stream.

When the video player 222 requests the manifest file from the manifest server 224 a connection is established between the devices. A session identifier is also generated to identify the connection. The session identifier may be generated by the video player 222 or the manifest server 224. For purposes of illustration, it will be assumed that the session identifier is generated by the video player 222. The session identifier is transmitted to the manifest server 224 by the video player 222 when requesting a manifest file. The manifest server 224 then requests the manifest file from the CDN 218 at block 242. At block 244, the CDN 218 returns the manifest file to the manifest server 224.

Because the manifest server 224 has established a connection with video player 222, it may customize the manifest file prior to returning the manifest file to the video player 222 and provide a unique manifest file to each video player 222. Without the manifest server 224, the video player 222 retrieves the manifest file directly from the CDN 218 and the content of the manifest file is the same for all users. However, because the manifest server 224 is providing a unique manifest file to each player, the manifest file may include identifying information of the video player 222, the user 225 of the video player, or a combination thereof. Further, the manifest file may be modified to include content specific for the user 225.

The manifest server 224 may be configured to generate an encryption key for each manifest file. The encryption key is generated as a function of the unique session identifier generated by the video player 222 when it requested the desired video content. Optionally, the encryption key may also be generated as a function of the requested video content. As a result, each encryption key is unique to a specific session with a particular video player, resulting in a one-time use unique encryption key. The one-time use unique encryption key will be referred to herein as the manifest encryption key. At block 246, the manifest server 224 transmits the manifest encryption key to the key server 226, and at block 248, the key server 226 acknowledges receipt of the manifest encryption key.

Optionally, the key server 226 may be configured to generate the manifest encryption key. At block 246, the manifest server 224 transmits the session identifier and an identifier corresponding to the desired video content to the key server rather than transferring the manifest encryption key. The key server 226 may then generate the manifest encryption key and, at block 248, return the manifest encryption key to the manifest server 224. After generating or obtaining the manifest encryption key, the manifest server 224 encrypts the manifest file prior to transmitting the manifest file to the video player 222. The manifest server 224 then transmits the encrypted manifest file to the video player 222, as shown at block 250.

Referring again to FIG. 6, if the video player 222 includes an enhanced video player module 229 from the provider of the manifest server 224, the enhanced video player module 229 may be configured to decrypt the encrypted manifest file directly. The manifest encryption key is encrypted in a manner known to both the manifest server 224 and the enhanced video player module 229. Therefore, the enhanced video player module 229 first decodes the manifest encryption key and then decodes the remainder of the manifest file using the manifest encryption key. If, however, the video player does not include an enhanced video player module 229 from the provider of the manifest server 224, the manifest server 224 may include a path to the key server 226, similar to that shown in FIG. 5, and the video player 222 requests the manifest encryption key from the key server 226 as shown in block 252. At block 254, the key server 226 returns the manifest encryption key to the video player 222, and the video player 222 decrypts the manifest file. Having decrypted the manifest file, either directly on the video player 222 with an enhanced video player module 229 or by requesting the manifest encryption key from the key server 226 and then utilizing the native video player module 228 to decode the manifest file, either the enhanced video player module 229 or the native video player module 228 next needs to decode the video content.

In some embodiments, the manifest file may remain unencrypted. When the manifest file is to remain unencrypted, the manifest server 224 may still generate a unique manifest file for the session with the video player 222. The operations in FIG. 7 process as discussed above from block 230 to block 244. However, rather than encoding the manifest file, the manifest server 224 skips blocks 246 and 248, transmitting an unencrypted manifest file to the video player at block 250. The video player 222 reads the manifest file and determines that the video content has been encrypted and, therefore, must still be decrypted.

The video player module reads the location of the key server 226 for the content encryption key from the manifest file. It is contemplated that a single key server 226 may contain both the manifest encryption key and the content encryption key. Optionally, separate key servers 226 may be utilized for each of the encryption keys. The video player 222 requests the content encryption key from the key server 226 identified in the manifest file, as shown in block 256. At block 258, the key server 226 returns the content encryption key to the video player 222. The manifest file will have the address of the CDN 218 as containing the segmented video content. Therefore, the video player can then start retrieving the video content from the CDN. The video player 222 repeatedly requests the next segment in the playlist from the CDN 218 and the CDN returns the requested segment as shown by blocks 260 and 262. The native video player module 228 then decodes the content from the encrypted video segments and displays the requested video content to the user 225.

Turning next to FIG. 8, a user interface 300 may be provided that is executing on the video manager 215. The user interface 300 receives input corresponding to desired control of or action to take on the video player as the video content is being presented to the video player 222. The user interface 300 includes a frame viewer 310 to display the video content on a frame-by-frame basis in order to synchronize metadata with a particular frame of the video content. The user interface 300 further includes an event selector 320 to identify a desired action to be taken on the video player 222. The selected event is encoded as metadata, for example, as an ID3 tag for insertion into the video stream.

Video players 222 are increasingly interactive devices, such as a laptop or tablet computer, a mobile phone, and the like rather than a passive viewing device such as a traditional television. The video player 222 may include a number of native applications, such as a calendar app, web browser, or social media plug-in. The event selected for inclusion as metadata may activate one of the native applications for an enhanced viewer experience. For example, a programming change may launch the calendar app and create an appointment for the calendar. The appointment may identify the new time for a program with a prompt to the viewer allowing the viewer to accept the appointment for insertion onto their calendar. As another example, the event selected may launch the web browser with a window providing additional content, such as a show website or a list of links to websites with subject matter related to a documentary. A viewer may choose to follow one of the links presented. As still another example, the event may launch a social media plug-in asking a user to indicate whether they liked a show or to provide a review of a show on their social media account.

According to another aspect of the disclosure, the metadata may be related to advertisement. Rather than simply provide an advertisement to be displayed on the video player 222, the advertisement may be interactive requiring a viewer to click on one or more boxes, buttons, and so forth, within the advertisement. The prompt to the viewer needs to be displayed at the correct frame within the advertisement so the viewer understands what is being requested. Optionally, the prompt may request a viewer to select from one of multiple advertisements for viewing, delivering content more attractive to a viewer. The metadata may further include instructions to the video player 222 to transmit the viewer interactions back to the user interface 300 for measuring.

According to still another aspect of the disclosure, the metadata may be related to the content of the programming. For example, the viewer may want to watch a live sporting event. However, a number of playback rules may be in place with respect to the event. The playback rules may include, for example, geographic blackout restrictions or geographic transmission of particular events, such as a local team. The live sporting event may run either less than its allotted time or beyond its original time slot. While playback rules may initially have been transmitted according to the original schedule, the rules may need to be updated, for example, to enforce a blackout beyond the schedule when an event runs long or to allow alternate programming to be viewed if an event runs short or is cancelled, for example, due to weather. In addition, it is desirable that the rules are enforced at particular frames to provide for clear transitions to or from the live event and the alternate programming.

According to still another aspect of the disclosure, the metadata may be inserted within the transport stream (TS) file containing the video content. As the encoder 214 receives the video signal 212 from the content provider 210, any triggers inserted within the video signal 212 by the content provider 210 are detected. The video manager 215 receives the triggers and identifies the metadata content corresponding to the trigger. The video manager 215 retrieves the video content from the content server 217. Optionally, the video manager 215 receives metadata and a frame reference from the user interface 300. The video manager 215 may encode the metadata according to the requirements of the transport stream into which it is being inserted or the video manager 215 may transmit the metadata to the encoder 214 where it is encoded. The transport stream includes a metadata stream which includes the content of the metadata (e.g., text or graphic to display, application to launch, playback rule, etc...) and the frame at which the metadata is to be displayed or activated. The metadata is then transmitted within the transport stream to the video player 222 as discussed above.

According to still another aspect of the disclosure, the metadata is inserted in the manifest file for transmission to the video player. The video manager 215 receives the trigger from the video signal 212 or receives the metadata from the user interface 300 as previously discussed. A custom tag is defined for insertion into the manifest file. The custom tag includes the content of the metadata and the frame reference at which the metadata is to be displayed or activated. The custom tag is inserted into the playlist of the manifest file and transmitted to the video player 222 as discussed above. Insertion of the custom tag into the manifest file may occur either with the encoder 214 or with the manifest server 224. According to one embodiment, the video manager 215 transmits the custom tag to the encoder 214 as the video signal 212 is being encoded. The custom tag is inserted into the manifest file generated by the encoder 214 and stored in the CDN 218. The manifest server 224 initially reads the manifest file from the CDN prior to generating a per-user manifest file and, therefore, the custom tag will be in the manifest file. According to another embodiment, the metadata may be provided at delivery rather than when the original video stream was encoded. The custom tag may be transmitted from the video manager 215 to the manifest server 224 and inserted into the per user manifest file by the manifest server 224.

The video player 222 receives the transport stream and manifest file for the requested video content into which the manifest data has been inserted. Either the native video player module 228 or the enhanced video player module 229 may be used to extract and act on the embedded metadata. If, for example, the metadata is inserted into the transport stream, the native video player module 228 receives the transport stream and processes the metadata. However, rather than receiving just a trigger, the transport stream includes the metadata content and the video player 222 may take the requested action without requiring an out-of-band connection. Similarly, if the metadata is inserted into the manifest file with a custom tag, the enhanced video player module 229 recognizes the tag and creates a metadata stream within the video player 222. The enhanced video player module 229 inserts the metadata stream in the transport stream at the correct frame location. Whether the metadata is inserted into the transport stream or the manifest file, the requested action occurs on the video player 222 at the desired frame of the video content without requiring an out-of-band connection to retrieve content.

In one aspect of the disclosure, a method is provided to inject per-user, per session metadata for advertising or other alternative content (for measuring) that is received from an alternative content server for the particular user-session in a manifest file for delivery to a user's video player.

According to another aspect of the disclosure, a method is provided for creating frame accurate triggers in a video transport stream from metadata that is injected into the manifest file by a per-user manifest delivery system (manifest server). This may allow a video player to provide a notification, such as to a server, with each metadata trigger event, with per frame accuracy.

According to another aspect of the disclosure, a method is provided for a user to interact with advertising or other alternative content (which may be stitched together with requested video content) using metadata triggers and action which may be directed by such metadata triggers. In one aspect, an action may include retrieval of information upon user can triggering the action by clicking on the alternative content as it is displayed.

According to another aspect of the disclosure, a method is provided for measuring advertising or other alternative content for a live stream stitched by a server using frame accurate triggers that are inserted by the system.

According to another aspect of the disclosure, a system is provided which may address the problem measuring advertising or other alternative content accurately when the advertising or other alternative content is stitched together with by a separate server (in which case a video player is only receiving video files and not measuring information embedded in the original advertising or other alternative content).

According to another aspect of the disclosure, a hardware or software module may be implemented in a video player in order to: process a unique video manifest file loaded from manifest server; parse the manifest file, which contains alternative content measuring information; process the manifest file to obtain gross-net times for every alternative content segment; and inject measuring capability into the video stream (TS file) for the alternative content measuring information via frame accurate triggers. In this way, a modified video stream (TS file) is provided to the video player which may allow the video player to trigger to produce detectable events which may be measured by a server or other utility at desired times.

It should be understood that the disclosure is not limited in its application to the details of construction and arrangements of the components set forth herein. The disclosure is capable of other embodiments and of being practiced or carried out in various ways. Variations and modifications of the foregoing are within the scope of the present disclosure. It also being understood that the disclosure disclosed and defined herein extends to all alternative combinations of two or more of the individual features mentioned or evident from the text and/or drawings. All of these different combinations constitute various alternative aspects of the present disclosure. The embodiments described herein explain the best modes known for practicing the disclosure and will enable others skilled in the art to utilize the disclosure. 

We claim:
 1. A system for managing video playback comprising: a manifest server comprising a memory and a processing device coupled to the memory to: (a) receive a request from a video player on a user device to play a video stream comprising requested content, wherein the requested content is associated with a first manifest file created for the requested content and distributed to a first content delivery network; (b) upon receiving the request: (i) communicate with a first content delivery network to obtain, from the first content delivery network, the first manifest file stored at the first content delivery network, the first manifest file containing information for allowing the video player to play the requested content stored at the first content delivery network, and information for stitching alternative content with the requested content; and (ii) communicate with a second content delivery network to obtain information for allowing the video player to play the alternative content, and produce a detectable event in connection with the alternative content; and (c) modify, using a session identifier identifying a connection between the manifest server and the video player, the first manifest file obtained from the first content delivery network to produce a second manifest file unique to the video player having the request, the second manifest file identifying at least one of the video player or the user of the video player, and containing information for allowing the video player to play the requested content and the alternative content stitched with the requested content, and produce the detectable event in connection with the alternative content, wherein the detectable event associated with the alternative content is detectable during video streaming using the video player of the user and is distinguishable from detectable events associated with other video players or other users.
 2. The system of claim 1, wherein the detectable event is produced by a trigger.
 3. The system of claim 2, wherein the processing device is to instruct, based on the trigger, the video player to respond, the trigger occurring responsive to a frame of the alternative content starting or stopping.
 4. The system of claim 2, wherein the processing device is to instruct, based on the trigger, the video player to respond, the trigger occurring responsive to the alternative content reaching a midpoint.
 5. The system of claim 1, wherein the manifest server stitches segments of the alternative content between segments of the requested content according to the second manifest file.
 6. The system of claim 1, wherein the second manifest file includes the session identifier.
 7. The system of claim 1, wherein the playlist provides an address at which the video stream is to be retrieved and at least one of a data rate and a resolution for the video stream.
 8. The system of claim 1, further comprising a measuring server in communication with the manifest server, wherein the measuring server stores the detectable event.
 9. The system of claim 1, wherein the detectable event associated with the alternative content is defined via metadata provided for the alternative content, and wherein the metadata defining the detectable event associated with the alternative content is included in a playlist of the second manifest file.
 10. The system of claim 1, wherein the processing device is further to: prior to transmitting the second manifest file to the video player, encrypt the second manifest file using an encryption key generated based on the session identifier.
 11. A method to manage video playback, the method comprising: (a) receiving a request from a video player on a user device to play a video stream comprising requested content, wherein the requested content is associated with a first manifest file created for the requested content and distributed to a first content delivery network; (b) upon receiving the request: (i) communicating with a first content delivery network to obtain, from the first content delivery network, the first manifest file stored at the first content delivery network, the first manifest file containing information for allowing the video player to play the requested content stored at the first content delivery network, and information for stitching alternative content with the requested content; and (ii) communicating with a second content delivery network to obtain information for allowing the video player to play the alternative content, and produce a detectable event in connection with the alternative content; and (c) modifying, using a session identifier identifying a connection between the manifest server and the video player, the first manifest file obtained from the first content delivery network to produce a second manifest file unique to the video player having the request, the second manifest file identifying at least one of the video player or the user of the video player, and containing information for allowing the video player to play the requested content and the alternative content stitched with the requested content, and produce the detectable event in connection with the alternative content, wherein the detectable event associated with the alternative content is detectable during video streaming using the video player of the user and is distinguishable from detectable events associated with other video players or other users.
 12. The method of claim 11, wherein the detectable event is produced by a trigger.
 13. The method of claim 12, further comprising instructing, based on the trigger, the video player to respond, the trigger occurring responsive to a frame of the alternative content starting or stopping.
 14. The method of claim 12, further comprising instructing, based on the trigger, the video player to respond, the trigger occurring responsive to the alternative content reaching a midpoint.
 15. The method of claim 11, further comprising stitching segments of the alternative content between segments of the requested content according to the second manifest file.
 16. The method of claim 11, wherein the second manifest file includes the session identifier.
 17. The method of claim 11, wherein the playlist provides an address at which the video stream is to be retrieved and at least one of a data rate and a resolution for the video stream.
 18. The method of claim 11, further comprising communicating with a measuring server that stores the detectable event.
 19. The method of claim 11, wherein the detectable event associated with the alternative content is defined via metadata provided for the alternative content, and wherein the metadata defining the detectable event associated with the alternative content is included in a playlist of the second manifest file.
 20. The method of claim 11, further comprising: prior to transmitting the second manifest file to the video player, encrypting the second manifest file using an encryption key generated based on the session identifier.
 21. A non-transitory computer readable medium comprising instructions, which when executed by a processing device causes the processing device to perform operations comprising: (a) receiving a request from a video player on a user device to play a video stream comprising requested content, wherein the requested content is associated with a first manifest file created for the requested content and distributed to a first content delivery network; (b) upon receiving the request: (i) communicating with a first content delivery network to obtain, from the first content delivery network, the first manifest file stored at the first content delivery network, the first manifest file containing information for allowing the video player to play the requested content stored at the first content delivery network, and information for stitching alternative content with the requested content; and (ii) communicating with a second content delivery network to obtain information for allowing the video player to play the alternative content, and produce a detectable event in connection with the alternative content; and (c) modifying, using a session identifier identifying a connection between the manifest server and the video player, the first manifest file obtained from the first content delivery network to produce a second manifest file unique to the video player having the request, the second manifest file identifying at least one of the video player or the user of the video player, and containing information for allowing the video player to play the requested content and the alternative content stitched with the requested content, and produce the detectable event in connection with the alternative content, wherein the detectable event associated with the alternative content is detectable during video streaming using the video player of the user and is distinguishable from detectable events associated with other video players or other users.
 22. The non-transitory computer readable medium of claim 21, wherein the detectable event is produced by a trigger.
 23. The non-transitory computer readable medium of claim 12, wherein the operations further comprise instructing, based on the trigger, the video player to respond, the trigger occurring responsive to a frame of the alternative content starting or stopping.
 24. The non-transitory computer readable medium of claim 12, wherein the operations further comprise instructing, based on the trigger, the video player to respond, the trigger occurring responsive to the alternative content reaching a midpoint. 